-
Notifications
You must be signed in to change notification settings - Fork 633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add TAG leadership election governance template #1195
base: main
Are you sure you want to change the base?
Add TAG leadership election governance template #1195
Conversation
Signed-off-by: leonardpahlke <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, made some suggestions to increase clarity.
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Show resolved
Hide resolved
tags/resources/tag-formation-templates/template-leadership-election-process.md
Outdated
Show resolved
Hide resolved
…ction-process.md Co-authored-by: Emily Fox <[email protected]> Signed-off-by: Leonard Vincent Simon Pahlke <[email protected]>
6c67f2b
to
1b9d268
Compare
Added the suggestions 👍 |
ref "Implementation of an updated TAG formation process" issue: #1043 |
I am thinking about splitting the document into two parts.
I think the procedure for working group and project leads can be simplified. |
@leonardpahlke, agreed. Since working group and project leads are a different process, than TAG Chairs and TAG TLs it makes sense to separate them. |
Sorry about the delay with lots of travel, I will review this this week and make sure the doc content is also merged in: https://docs.google.com/document/d/1xP1SXy4LW9yxI_1cs3GYQyv6wb3-JYBdXE8MYO0RnqQ/edit?usp=sharing |
Hi @leonardpahlke this looks great. Based on our prior discussion, do you think we can add the following as well? Leadership Terms: Elections: For the immediate election in 2025, roughly 50% of the roles should be made available for election where existing leaders can choose to rerun, starting with the longest serving leaders. The rest of the leads who are not up for election should plan to be up for elections in 2026. Co-chairs can be nominated by any existing co-chairs or TOC member. TL roles should be nominated by any existing co-chairs or TLs. WG leads can be nominated by any TAG leaders.TAGs may define their own process by which they field nominations for these roles, provided they adhere to CNCF and TOC expectations of openness, transparency, and accountability. Co-chair elections should be voted on by the TOC. Other TAG leads elections should be voted by TAG co-chairs, TLs, WG leads or other active members of the TAG. Vacancies Liaisons |
|
||
**Nominees must**: | ||
|
||
* Be the author of at least one pull request against the `<TAG NAME>` repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A quick question: What is the purpose of calling this out versus making it part of the list below? It seems to already be somewhat related to the commenting on PRs, etc. issue below.
Is the author of a PR the person who created it? Is any person who did a lot of the work on it an author? What about someone who reviewed and commented heavily on it? Do all PRs regardless of length / purpose / complexity count the same here?
I know this is all subjective and I'm not proposing to define all the corner cases. I'd actually prefer to make this less specific and less emphasized. My concern is that I don't want someone with imposter syndrome who has been a great contributor, but who didn't create a PR to feel like their application shouldn't be put forth.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are good points @JustinCappos.
If i understand it correctly, the intent here was to define observable metrics to confirm that individuals being nominated are familiar with, have performed, and contributed meaningfully to the TAG. Since the existence and governance of the TAGs are managed and orchestrated through GitHub, its important to confirm such activity has occurred therein.
Given the collaborative nature of many pull requests from our TAGs, it is reasonable to expect that over the course of a potential candidate's involvement in the TAG that they have assisted in triaging, reviewing pull requests, updating/changing/creating new content in the TAG repo, and performed other git observable and trackable activities that demonstrate a deeper level of active involvement in the group's success beyond discussions and slack messages. Effectively demonstrating skills, management, and forethought that we would expect from the leaders of our TAGs.
Would other's confirm my understanding?
Thanks for the input. Will make updates to the PR this week. |
@leonardpahlke any update on this? |
Signed-off-by: Leonard Pahlke <[email protected]>
3611e75
to
807c058
Compare
Updated the PR. @linsun please take a look.
I am wondering if this would be better placed in the roles document, since It's not really about the election, right? |
This PR adds a template under the
toc/tags/resources/tag-formation-template
to document the leadership election process within TAGs. This PR #1086 established the/tags/resources
structure, and this PR adds content to one of the empty stub files. More PRs will follow to add content to the other template files (like: #1128 and #1116).The election process is a combined version of the TAG ENV TL, TAG ENV Chair and TAG ENV WG Chair election process. TAG ENV originally pulled the governance files from TAG Security, see file.